tests: unit: ble_adv: improvements to ble_adv testcase configs#656
Conversation
|
Changes to a unit test. No changelog entry needed. |
|
You can find the documentation preview for this PR here. |
Does it? It seems that we disable some modes instead of enabling the mode we want to test. |
I was referring to the "list" of modes in the testcase names. Not what configs are disabled or enabled. |
| @@ -4,24 +4,29 @@ common: | |||
| tags: unittest | |||
There was a problem hiding this comment.
Just a thought, will discuss offline, would it be an idea to turn off all modes in prj.conf, then enable everything here based on the test case? Could give a better overview of what is enabled for the different tests.
There was a problem hiding this comment.
Thanks. The second commit now disables every advertising mode in prj.conf so that the desired modes can be (re)enabled in testcase.yaml. I think it should be more readable and maintainable now.
6dc22d7 to
82f6b65
Compare
The no_directed_hd_or_fast and no_directed_hd_or_slow test configurations was missing CONFIG_BLE_ADV_DIRECTED_ADVERTISING=y. In addition, align the order of configs. Signed-off-by: Andreas Moltumyr <andreas.moltumyr@nordicsemi.no>
To increase readability and maintainability, rework testcase logic to list what modes are enabled instead of listing what modes are disabled. To achieve this, disable all advertising modes in the prj.conf file. Signed-off-by: Andreas Moltumyr <andreas.moltumyr@nordicsemi.no>
82f6b65 to
b925db4
Compare
First commit fixes missing directed advertising configuration for two of the test cases.
Second commit reworks the testcases to list what modes are enabled instead of listing what modes are disabled.